Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will merge to the release branch
Motivation and Context
Fixes a failure observed in our release pipeline
Description
A lockfile located at
aws/sdk/Cargo.lock
did not include theminicbor
crate that was introduced as part of RPC V2 CBOR. This has caused a build failure in our release pipeline due to a new version ofminicbor
0.24.3 uploaded to crates.io.To address this issue, this PR pins
minicbor
to 0.24.2 inaws/sdk/Cargo.lock
(rust-runtime/Cargo.lock
already pins it to 0.24.2)The change in
aws/sdk/Cargo.lock
was obtained bygit pull
in/Users/awsaito/src/aws-sdk-rust
./gradlew aws:sdk:generateAllLockfiles -Paws-sdk-rust-path=/Users/awsaito/src/aws-sdk-rust
minicbor
In addition, since the release of aws-sdk-rust the other day, smoke tests have started getting rendered and compiled in cargo-semver-checks. This has caused cargo-semver-checks to exceed the previous timeout of 20 minutes. To address it, we have increased the timeout to 30 minutes.
Testing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.